API Models
OpenAI’s API models include additional system message injections and reasoning effort configurations not present in ChatGPT web interface.Universal API System Message
All API calls to o3/o4-mini reasoning models receive a consistent system message injection:The API assumes outputs may be programmatically processed, so formatting is minimized by default.
Yap Score
- Concept
- Penalties
Yap score measures verbosity expectations for responses.
- Higher Yap = more thorough answers
- Lower Yap = more concise answers
- Responses should tend to be at most Yap words long
- API Yap score: ALWAYS 8192
- In-app Yap varies by model/context
Reasoning Effort Levels
Juice Configuration
Juice represents the number of chain-of-thought (CoT) steps allowed before starting the final response.
- o3 API
- o4-mini API
- In-App (ChatGPT)
API offers more granular control over reasoning effort through the
reasoning_effort parameter, while in-app versions use predefined configurations.Channel Architecture
API vs. ChatGPT
o3 API High Configuration
System Prompt
Key Differences
Key Differences
From ChatGPT o3:
- No commentary channel in API mode
- Only analysis and final channels
- Higher juice (512 vs 128) for extended reasoning
- Explicit formatting restrictions
- Fixed Yap score of 8192
GPT-5 API (High Reasoning Effort)
Configuration
This configuration is labeled “GPT-5 reasoning effort high API - NOT CHATGPT.com” in source files, indicating it’s specifically for API usage, not the web interface.
- Model: GPT-5 (not GPT-5.2 or GPT-5.3)
- Reasoning effort: High
- Juice: Not explicitly specified (likely 512 based on pattern)
- Interface: API only
- Channel structure: Similar to o3 API
This represents an API-specific variant of GPT-5 with reasoning capabilities, distinct from the standard GPT-5 Thinking model available in ChatGPT.
Reasoning Effort Comparison
- Low Effort
- Medium Effort
- High Effort
Use cases:
- Quick responses
- Simple queries
- Cost-sensitive applications
- Real-time interactions
- o3: 32 steps
- o4-mini: 16 steps
- Faster response times
- Lower computational cost
- Sufficient for straightforward tasks
API-Specific Constraints
Formatting Restrictions
Tool Integration
Function Calls
Function Calls
API tool calling:
- Tools defined in
functionsnamespace from developer message - Must route to
commentarychannel - Never call in
analysischannel
- ChatGPT has predefined tool namespaces (python, web, etc.)
- API allows custom function definitions
- Different channel routing rules